Run test_medium_seamless_m4t_pt in subprocess to avoid many failures#34812
Merged
Run test_medium_seamless_m4t_pt in subprocess to avoid many failures#34812
test_medium_seamless_m4t_pt in subprocess to avoid many failures#34812Conversation
ydshieh
changed the title
test_medium_seamless_m4t_pt for nowtest_medium_seamless_m4t_pt in subprocess to avoid many failures
|
The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update. |
BernardZach
pushed a commit
to BernardZach/transformers
that referenced
this pull request
Dec 5, 2024
…res (huggingface#34812) * fix * fix * fix --------- Co-authored-by: ydshieh <ydshieh@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
This (pipeline) test
is always failing all the time.
Previously, the pipeline test is running on CPU, but after #34026, it's running on GPU if available.
And with the issue #34811, this failed test affect many subsequent pipeline tests because of